Release 10.1A: OpenEdge Development:
Web Services


Typical SOAP fault response message

The following is the content of a typical SOAP fault response that appears within the body of a WSA-generated SOAP fault message:

<soap:Fault> 
  <faultcode>SOAP-ENV:Server</faultcode> 
  <faultstring>An error was detected … request. (10893) </faultstring> 
  <detail> 
    <ns1:FaultDetail soap:encodingStyle=“http://schemas.xmlsoap.org/…/” 
      xmlns:ns1="http://servicehost:8080/wsa/wsa1"> 
      <errorMessage xsi:type=“xsd:string"> 
        The urn:OrderSvc:OrderInfo service is unavailable (10921)  
      </errorMessage>  
      <requestID xsi:type=“xsd:string"> 
        2e62cab6b81150d5:-17c6a3c:f1dffbd11b:-8000#1f 
      </requestID>  
    </ns1:FaultDetail> 
  </detail> 
</soap:Fault> 

Note that SOAP faults can be returned by the client’s own SOAP libraries and might have a different XML definition for the contents encapsulated by the <detail> element, depending on the Web service client toolkit that is used. However, a SOAP fault generated by the OpenEdge WSA always includes an <error Message> and <requestID> element within the <detail> element section.

WSA’s <errorMessage> element

The SOAP <faultstring> element provides only a very general description of the error. For the most effective diagnostic detail, always look at the information provided by the <errorMessage> element.

WSA’s <requestID> element

Use the information provided by the <requestID> element when you contact the Web service deployer for assistance with an error. This information tells the Web service deployer whether more information can be obtained from the WSA log file. For more information on how the WSA uses the information in the <requestID> element to log information, see the "How the WSA logs Web service information" section.


Copyright © 2005 Progress Software Corporation
www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095